-
Notifications
You must be signed in to change notification settings - Fork 163
Document OTel integrations for Fleet-managed Elastic Agent #3530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔍 Preview links for changed docs |
79702fa
to
738cc0d
Compare
738cc0d
to
f4834c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks!
@vishaangelova thank you this looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent work! Left some comments.
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the heads up, Visha. We both made some similar and contradictory changes to the Manage topic, but I can sort it out when my PR is ready. LGTM
This PR documents the added support in Fleet for OTel integrations packages in a new doc ("Collect OpenTelemetry data with Elastic Agent integrations”), placed under Manage Elastic Agent integrations.
It also makes some small improvements to the content structure of the doc (removing an admonition, adding a heading and a reference to the OTel integrations doc).
Resolves elastic/ingest-docs#1861
Preview